Improve logging and estimation in WarmCache process #16083
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Feature
What does this PR do? Why is it needed?
The WarmCache process currently logs a generic message when it starts, but it does not provide any progress updates or an estimated time for completion. This lack of visibility can cause confusion for users, especially when the process takes a long time (e.g., hours). Users are left wondering whether the process is stuck or how much longer it will take.
Which issues(s) does this PR fix?
This PR fixes the issue related to Issue #16054 to improve the logging during the WarmCache process in the BlobStorage implementation
Fixes Issue #16054
Other notes for review
Acknowledgements